Subject: *EffCap* objects

From: "Mark C. Regan" <[email-masked]>
Date: Fri, 27 Oct 95 9:06:26 PDT

All of the effective capacity objects are currently represented
by an integer value that is the expanded version of the byte
version.  A problem arises when two nodes (implementing the MIB)
return the effective capacity of the same TG and the floating
point logic is different in the two nodes.  This causes the
application to receive two different values for effcap when they
are actually the same.

PROPOSAL: change the SYNTAX of all effective capacity objects
to be a byte (or INTEGER(0..255)).  This is the approach taken for
propogation delay and we should be consistent.  If there is a
concern about having the application do the decode, we can 
supply the algorithm in the description.  But it is spelled out
in the architecture also.

   Effected objects:
    appnNnTgFREffCap
    appnLocalTgEffCap
    appnLocalEnTgEffCap
    appnCosTgRowEffCapMin
    appnCosTgRowEffCapMax
--------------------------------------------------------------
Mark C. Regan         "Where's the kaboom?  There was supposed
Cisco Systems, Inc.    to be an Earth-shattering kaboom!"
(770) 984-2867         - Marvin the Martian